Fix visual mode e behaving like w#53
Merged
Merged
Conversation
Previously e in visual mode was mapped to the same host command as w (input.select.word.forward), making them behave identically. This adds a dedicated handler that reuses the existing endOfWord() computation and emits a selectRange from the visual anchor to the correct offset. Closes #52
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Visual mode
ewas mapped toinput.select.word.forward(the same host command asw), so both moved to the start of the next word instead of the end of the current one.This adds a dedicated
ehandler inhandleVisualKeythat reuses the existingendOfWord()helper and extends the selection from the visual anchor to the computed offset. Also introducesvisualAnchoronVimState, tracked onv/Ventry, so custom motions in visual mode know where the selection started.Closes #52